Customizable Macro-Based Order Entry Protocol and System

ABSTRACT

The present technology is related to employing a template/macro-based order entry system. An initial order data message contains a macro that establishes the initial parameters for an order and a unique ID is associated with the template. Subsequent, and potentially smaller sized data messages contain the unique ID as well as relevant order details for placing an order. Of course, the technology described herein envisions a much broader concept of reducing message sizes to help improve overall latency and is not limited to order entry.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation U.S. Pat. Application No. 16/803,087, filed Feb. 27, 2020, which is a continuation of U.S. Pat. Application No. 14/840,820 filed Aug. 31, 2015 (now U.S. Pat. No. 10,607,289), which is a continuation of U.S. Pat. Application No. 14/055,205 filed Oct. 16, 2013 (now U.S. Pat. No. 9,123,076). The entire contents of each of these applications are incorporated by reference in their entirety.

BACKGROUND

The technology provides decreased payload, decreased latency and conservation of bandwidth by using a new and inventive protocol method and corresponding system. The technology is specifically related to order data message entry and in particular to a Macro-based order entry methodology which, among other things, allows for reduced messaging between exchange clients and an Order Port/Gateway of an exchange.

In modern distributed systems, billions of data messages are passed between separately located devices in only fractions of a second. Although modem computing devices have larger memories, faster processors, and greater broadband capabilities, there is always a need to improve upon processing efficiency and overall latency between the devices. This can be especially true for electronic exchange systems that communicate with numerous remote devices and conduct order entry and order processing on a mass scale.

Certain modem exchange systems use the OUCH Order Entry Protocol for order entry. The OUCH protocol is a proprietary NASDAQ OMX® digital communications protocol that allows customers of electronic exchange providers to conduct business in various electronic, financial markets. With OUCH, subscribers can place, execute, or cancel orders. OUCH moreover allows subscribers to integrate electronic exchange services into their proprietary networks, giving a rather high degree of seamlessness. OUCH is a low-level, native protocol designed for high performance and minimal latency. In order to achieve optimum functional efficiency and speed, some flexibility is sacrificed.

The OUCH protocol passes logical messages, of a specific length, between the host (i.e., exchange) and the client (i.e., trader) application. All data messages sent to the host can be retransmitted in the event of a temporary hardware failure or software error. By connecting a single OUCH account to more than one machine, redundancy and fault tolerance are achieved. Moreover, OUCH ensures that data messages from customers (brokers/traders/members) are processed in the same sequence as they are received. Each new order contains a token specifying the date and the name of the account. Once a token has been used it automatically expires so it cannot be used again. When an order has been placed, executed, or canceled, and the action has been accepted by the host, an acknowledgment data message is sent to the client.

Inbound (client-to-host) messages can include, but are not limited to, the following types: Order entry, Cross order entry and Order cancellation entry. Outbound (host-to-client) messages can be more diverse, including, but not limited to: Start of day, End of day, Time stamp, Order request, Order acceptance, Order rejection, Order execution, Cancel pending, Cancel rejection, Order cancellation, Broken trade and Price correction.

The OUCH protocol is composed of logical messages passed between the OUCH host, and client applications. Each message type has a fixed message length and all messages are composed of fixed length. The data types used are numeric fields, which comprises a string of ASCII-coded digits, right-justified and zero-filled on the left; and alpha fields, which are left-justified and padded on the right with spaces.

A new order message, entered via OUCH, must specify all required fields, and the Order Entry Port must parse and validate every one of those fields. It is commonly the case that users of OUCH and similar order entry protocols (for example, the FIX protocol) will submit a series of messages that are identical except for a small subset of available fields. This duplicated information must be carried over communications infrastructure, managed by hardware in Exchange data centers, and processed by Exchange systems. With the available conventional technology, there is no way to avoid the transmission of this duplicative information by a user, and moreover, the Exchange has no way to avoid processing it. Thus, there is a need for a system that can reduce submission of duplicate information while improving latency between separate devices.

BRIEF SUMMARY

The present technology addresses these problems by using a template/macro-based order entry system. An initial order data message contains a macro that establishes the initial parameters for an order and a unique ID is associated with the macro. Subsequent, and potentially smaller sized data messages contain the unique ID as well as relevant order details for placing an order. Of course, the technology described herein envisions a much broader concept of reducing message sizes to help improve overall latency and is not limited to order entry.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example function block diagram of an exchange system;

FIGS. 2A-D depict example diagrams of order data messages and respective contents of the order data messages;

FIG. 3 is an example application flowchart for a system employing an order entry protocol structure;

FIG. 4 is an example application flowchart for a system employing an order entry protocol structure to process the order data messages; and

FIG. 5 is an example of contrasting message types.

DETAILED DESCRIPTION OF THE TECHNOLOGY

In the following description, for purposes of explanation and non-limitation, specific details are set forth, such as particular nodes, functional entities, techniques, protocols, etc. in order to provide an understanding of the described technology. It will be apparent to one skilled in the art that other embodiments may be practiced apart from the specific details described below. In other instances, detailed descriptions of well-known methods, devices, techniques, etc. are omitted so as not to obscure the description with unnecessary detail. Individual function blocks are shown in the figures. Those skilled in the art will appreciate that the functions of those blocks may be implemented using individual hardware circuits, using software programs and data in conjunction with a suitably programmed microprocessor or general purpose computer, using applications specific integrated circuitry (ASIC), and/or using one or more digital signal processors (DSPs). The software program instructions and data may be stored on non-transitory computer-readable storage medium and when the instructions are executed by a computer or other suitable processor control, the computer or processor performs the functions. Although databases may be depicted as tables below, other formats (including relational databases, object-based models and/or distributed databases) may be used to store and manipulate data.

Although process steps, algorithms or the like may be described or claimed in a particular sequential order, such processes may be configured to work in different orders. In other words, any sequence or order of steps that may be explicitly described or claimed does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order possible. Further, some steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to the invention(s), and does not imply that the illustrated process is preferred. A description of a process is a description of an apparatus for performing the process. The apparatus that performs the process may include, e.g., a processor and those input devices and output devices that are appropriate to perform the process.

Various forms of computer readable media may be involved in carrying data (e.g., sequences of instructions) to a processor. For example, data may be (i) delivered from RAM to a processor; (ii) carried over any type of transmission medium (e.g., wire, wireless, optical, etc.); (iii) formatted and/or transmitted according to numerous formats, standards or protocols, such as Ethernet (or IEEE 802.3), SAP, ATP, Bluetooth, and TCP/IP, TDMA, CDMA, 3G, etc.; and/or (iv) encrypted to ensure privacy or prevent fraud in any of a variety of ways well known in the art.

Example components of a Macro Based Order Entry Protocols can include a macro definition message which is a message that instructs the system to define values for static fields and or a sequence of order management messages that will be subsequently inferred by the system. Another component includes a macro definition validation system that validates that macro orders have static values and/or the sequence of messages that can be sensibly accepted by the system. This system could, for example, be integrated into an order entry port. It should also be appreciated that the macro can also be referred to as a template.

The system also includes a macro definition acknowledgement which is a message sent by the system to alert the user of the successful initialization of the macro, and the identifying information for that macro as assigned by the system. Included also is a macro which contains values for static fields and/or a sequence of order management actions defined by a Macro definition message together with its identifying information as stored and recognized by the system.

The system also includes a macro order message which is a message containing instructions relating to an actual order, including a reference to a Macro via its identifying information as well as relevant non-static information that is required to successfully generate a valid order and/or sequence of events per the underlying protocol. The system also includes a macro order message interpreter which is a system for generating appropriate order management actions based on the combined specifications of the macro and the macro order message.

Users can interact with the Macro Based Order Entry Protocol System first by submitting a Macro definition message which is validated by the System. The validation is both of content (such as validating that the broker submitting the message is entitled to do so), and also validating that the submitted order is allowed for trading (e.g., by verifying trading limits are not reached). Upon successful processing, a macro is created and acknowledged to the user. Subsequently, the user may submit a Macro order message (which is substantially smaller in size relative to traditional order messages) that is interpreted by the system using the information made available by the macro’s definition and additional non-static information included on the Macro order message. In this way, the system would be able to avoid processing (e.g. parsing validation) static fields each time Macro orders are received and improves greatly the operating efficiency of Exchange systems by reducing the amount of data that must be processed per transaction.

These macros may remain active for as long as the user determines to allow them to exist, or as long as the system has been configured to allow them to exist. The Macro Based Order Entry Protocol and System is provided for efficient communication and processing of incoming, or internally routed, client orders. The submitted macro may relate to a message or series messages for placing orders, cancelling orders, modifying orders, replacing orders, etc. or any combination thereof, in financial products including but not limited to equities, options, and/or derivative products. The macro structure allows for user customization or definition of the static portion of the order entry instruction (order type, symbol, time in force, etc.) which is parsed, validated, and initialized only subsequent to the definition of the macro by the user. Each use of the macro must specify only the non-static portion of the order entry instruction (side, price, etc.) allowing for expedited parsing, validation and processing by any components in the system.

The below-described non-limiting example uses a Pseudo Protocol to describe the communicated messages. The actual protocol can be represented in binary format. The System in the example may represent a Matching Engine, an Order Router, OMS, EMS, or any other node or component in an exchange system involved in processing or otherwise handling orders.

A user node (e.g., trader/broker/member) transmits a Macro definition data message with an instruction to create a macro, specifying all of the static portions of the order and/or the desired series of order management actions to be represented by the order. An order port processes the message in which the processed message would be passed to the system. In this example, the user sets a macro to send an order for 100 shares of NDAQ® with a time in force of Immediate or Cancel. An example of the order could be represented as: MACRO_CREATE LIMIT _ORDER [SIDE] NDAQ 100 [PRICE] IOC

The Order Port, which includes a Macro definition message validation system, receives, parses and validates all of the Static Fields in the message for valid Order Type, Symbol, Order Size, and Time In Force. Once validated, the Order Port forwards the Macro definition message or materially the same information to the order processing system, in this example an Exchange matching engine.

The System receives the information from the order entry port, and creates an object representing the macro and sends a Macro definition acknowledgement to the user about the successfully allocated Macro. A Macro ID will be unique on a per user basis and an example of the acknowledgment could be represented as: MACRO_CREATE_SUCCESS MACRO_ID=43

For each subsequent actual order, the client (e.g., trader/broker/member) submits a Macro order message to the order port, referencing the previously created macro, specifying just the variable portions of the order entry instruction. For example, the subsequent order data messages could be represented as:

-   MACRO_ORDER TEMPLATE_ID=43 BUY 29.50 -   MACRO_ORDER TEMPLATE_ID=43 SELL 29.60 -   MACRO_ORDER TEMPLATE_ID=43 BUY 29.55 -   MACRO_ORDER TEMPLATE_ID=43 SELL 29.65

The Order Port receives, parses, and validates only the variable fields in the context of the static order entry instructions. In the present example, the Order Port does not need to validate the Order Type, Symbol, Order Size or Time In Force, and only needs to check the Side and Price of the order. Once valid, Order Port forwards the information to the System.

The system receives the macro order, looks up the object containing the previously initialized static values, updates it with variable values and processes the object as it would otherwise. If, as in the present example, the system represents a Matching Engine, it would process the incoming Macro Order by combining the static-information contained in the appropriate Macro with the non-static information on the Macro Order and process this complete message as though it were a traditional message containing explicit instructions for each of the required fields.

In an example implementation of the macro system, a client (e.g., trader/broker/member) may submit up to 256 unique macros (or templates) that define a set of static values such as symbol, TIF, Firm, Display, Capacity and a set of variable values such as side, size, price, etc. Each subsequent Order Entry Command may be as small as 4 bytes; i.e. message type (1 byte), template Id (1 byte) and quantity (2 bytes) and price (2 bytes). The Order Entry port will only validate the template itself, consequently there will be minimal validation required for each subsequent Macro Order, with the exception of checks that, by their nature, must be done by the system for each processed order in order to allow for correct execution of the transaction, for example, in the case of US Equities price checks done for purposes of complying with Regulation National Market Sytem (NMS), Regulation Shortsale Handling Obligations (SHO), etc. An illustrative example of the contrasting message types is illustrated in FIG. 5 .

This present technology enables users of Exchange or Exchange-like systems to instruct these systems to generate complete order management instructions from a combination of pre-defined static instructions that need only be submitted once and instructions that are variable on an order by order basis. This technology has to potential to greatly reduce the costs of trading for nearly all securities, most immediately those that have already migrated to electronic Exchange platforms.

By providing all of the static components of order entry instruction in advance (especially during non-market trading hours), the system is utilized in processing and validating all of the required fields only once per macro. Furthermore, communications of variable components of order entry instruction are not only smaller in size (thus reducing bandwidth consumption), but also bypass previous static field validation routines, allowing for faster processing and determination execution path within an application. As an example, inbound client message size can be substantially reduced (to the extent that static fields are predefined by the user, meaning this information would no longer need be transmitted) and also client message quantity will be reduced to the extent that the macro represents a series of actions which would otherwise need to be independently undertaken by the user.

FIG. 1 is an example function block diagram of an exchange system. A computer-implemented exchange system 300 can be coupled via a network 200 to a client system 100 configured to create and place orders with the exchange 300. The client system 100 can be implemented with and/or used via a personal computer, a PDA device, a cell phone, a server computer, or any other system/device for conducting the electronic exchange described herein. The client system 100 can be any individual and/or business entity conducting electronic trading with the exchange. The exchange system 300 communicates with a plurality of client systems 100 to match orders.

The client system 100 includes a central processing unit (CPU) 101, a memory 102, a data transmission device 103, and an input/output (I/O) interface 104. The data transmission device (DTD) 103 can be, for example, a network interface device that can connect the client system 100 to the network 200. The connection can be wired, optical, or wireless and can connect over a Wi-Fi network, the Internet, or a cellular data service, for example. The data transmission device 103 is capable of sending and receiving data (i.e., a transceiver), such as order data messages created by an order creator 105. The I/O interface 104 can be, for example, a physical interface for communicating data, including, but not limited to an optical disc drive, a USB interface, and/or a memory stick interface. The client system 100 can be used for conducting exchange with the exchange system 300. The client system 100 can take an order from a user, created via the order creator 105, for a derivative instrument, send it to the exchange system 300, and the exchange system 300 can attempt to match the order.

The exchange system 300 includes an order processor 301 and a matching unit 302. The order processors includes a parsing unit 301-1 for parsing order data messages sent from the client device 100 and a validation unit 301-2 for validating the parsed order data messages. The order processor also includes a macro (or template) generator 301-3 that can generate a macro/template for order entry where subsequent orders can use a unique ID generated from the macro generator 301-3 for processing orders. The order processors 301 also includes an order generator 301-4 that can generate an order using the unique ID contained in the subsequent orders and matching that information with a template.

The matching unit 302 includes a CPU 302-1, a memory 302-2, a data transmission device 302-3, and an input/output (I/O) interface 302-4. In an example embodiment, the exchange system 300 may include multiple processors and/or memories and may be designed for fail-safe redundancy. The data transmission device (DTD) 302-3 can be, for example, a network interface device that can connect the exchange 300 to the network 200, and is capable of sending and receiving data (i.e. a transceiver). The I/O interface 302-4 can be, for example, a physical interface for communicating data, including, but not limited to an optical disc drive, a USB interface, and/or a memory stick interface.

The exchange system 300 also has a matching engine 302-5, implemented using one or more processors, for matching orders and an order book memory 302-6 for storing orders. The order book 302-6 can exist in the memory 302-2 of the exchange system 300.

FIGS. 2A-D depict example diagrams of order data messages and respective contents of the order data messages. As explained above, the client device 100 can create an order data message that is submitted to an exchange system 300. An initial order data message can comprise a list of fields having different values assigned for each field. For example, the client device 100 can create an initial order for 100 shares of NASDAQ OMX® (NDAQ) with a time in force of Immediate or Cancel. Upon receiving the initial order data message, the system 300 can create a macro definition message specifying all of the static portions and variable portions of the order and assign a macro ID to the order. An example of the macro definition message and its static and variable portions are shown in FIG. 2A. The macro definition message can have a macro ID TID, one or more static fields SF1-n, and/or one or more variable fields VF1-n.

The system 300 can match the initial order data message values with the fields as shown, for example, in FIG. 2B. The example shown in FIG. 2B uses the order for 100 shares of NDAQ as discussed above, and creates a macro ID TID 43 with static fields 1, 2, and 3 corresponding to the trading name/ticker NDAQ, the number of shares 100, and the time in force of Immediate or Cancel, respectively. The variable fields 1 and 2 correspond to the side (e.g., buy, sell) and the price, respectively.

Upon creating the macro, the system can send an acknowledgement to the device 100 informing the device that the macro was successfully created and providing the device with the macro ID 43. The macro ID can be unique on a per user basis, for example.

The device 100 can then send orders referencing the macro ID and providing data in the order only for the variable fields (as the static fields are already defined by the macro). FIG. 2C shows an example of the fields contained in a subsequent order where the order will have the macro ID TID and one or more variable fields VF1-n. For example, subsequent orders associated with macro ID TID 43, shown in FIG. 2D, could be for buying shares of NDAQ for 29.50 or 29.55 per share or selling shares of NDAQ for 29.60 or 29.65 per share. FIG. 2D reflects the “shortened” order data message having only the macro ID TID and the two variable fields VF1 and VF2. Thus, the system advantageously reduces the amount of data sent in the subsequent order data messages thereby greatly improving the latency between the device 100 and system 300 as less data will be submitted with each order message.

As explained above, conventional systems would simply submit the entire order message (shown in part in FIG. 2B) for each order where the side and price would change for each message. By creating a unique macro ID TID, the subsequent orders need only reference the TID and one or more of the relevant variable fields VF1-n thereby reducing the amount of data transmitted between the device 100 and the system 300. Even though this modification may not seem as significant for a single order, the latency when processing billions of order data messages is greatly reduced by this improvement. The system 300 can also parse and validate the initial and subsequent order data messages to ensure that the proper contents of the messages are present.

FIG. 3 is an example application flowchart for a system employing an order entry protocol structure. Although not limited to this embodiment, the processes shown in FIG. 3 can be carried out by the device 100 where the device will begin process by creating an initial order data message (S301). In the example shown above, the initial order data message could be an order for 100 shares of NDAQ with a time in force of Immediate or Cancel. Upon creating this initial order data message, the system will transmit the order data message (S302) via the DTD 103 to the system 300. As described in further detail below, the system 300 can send an acknowledgement back to the device 100 and/or subsequent messages indicating the success or failure of processing/matching the order.

Upon sending the initial order data message, the device 100 will ideally receive an acknowledgement (S303) from the system 300 having a macro ID TID. The device 100 can use this macro ID in creating one or more subsequent order data messages (S304) where the TID and relevant variable fields VF1-n will be used in the subsequent order data messages. These subsequent order data messages can then be transmitted to the system 300 for matching (S305).

FIG. 4 is an example application flowchart for a system employing an order entry protocol structure to process the order data messages. Although not limited to this embodiment, the processes shown in FIG. 4 can be implemented by the system 300.

The system 300 begins by receiving the initial order data message (S401) from the device 100. Using the example from above, the initial order data message can be an order for 100 shares of NDAQ with a time in force of Immediate or Cancel. The system 300 can validate the initial order data message (S402) by parsing the order data message to ensure that the proper fields contain the proper types of data for each field. The system 300 can also validate that submission was correct (e.g., by a member of the exchange and that said member is allowed to trade at specified order volumes). For example, an order data message having a numeric value for the trading name (e.g., NDAQ) may not pass validation (unless of course there are trading names that happen to contain a numeric value). Upon successful validation the system will generate a macro ID TID for the initial order data message (S403) and then submit an acknowledgement of the initial order data message (S404) containing the macro ID TID in the message to the device 100.

The device 100 can then create subsequent order data messages that contain the macro ID TID and the system 300 will receive these messages containing the TID (S405). The system 300 can then combine the subsequent order data messages (for example, by concatenating) with the static fields in the macro. For example, a subsequent order for NDAQ having a sell designation for 29.50 per share will be combined with the macro to form an order message comprising both the static fields and variable fields resulting in the full order message of SELL NDAQ 100 29.50 IOC.

In this manner, the system can incorporate such an order management protocol without affecting the design of the exchange. That is, the order that is actually processed by the exchange will reflect a typical order, even though the message actually submitted to the exchange 300 contained less amount of information. Such an improvement increases the overall latency for order transmission and processing as less data is sent with each order while at the same time the order will appear as a normal order once it is ready for matching at the exchange. The system 300 can then attempt to match the order (S406) where the order will either match (408) or be stored in an order book (S407) for later matching.

While the technology has been described in connection with example embodiments, it is to be understood that the technology is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements. 

1. A system, comprising: a processor; and a memory configured to store computer readable instructions that, when executed by the processor, cause the system to: receive a first order data message, wherein the first order data message includes: one or more first fields; one or more second fields; and a first order having first field values associated with the one or more first fields and second field values associated with the one or more second fields; generate a first order template having the one or more first fields and the one or more second fields, the one or more first fields in the first order template including the first field values; receive a second order data message, wherein the second order data message is associated with the first order and includes third field values associated with the one or more second fields; validate the third field values in the second order data message; generate a complete order based on the validated third field values in the second order data message and the first field values in the first order template; and process order data included in the complete order.
 2. The system of claim 1, wherein the first order template is a macro definition message, and the macro definition message includes the one or more first fields, the one or more second fields, and the first order having the first and second field values.
 3. The system of claim 2, wherein the second order data message references the macro definition message using an order macro identifier (ID).
 4. The system of claim 3, wherein the system is further caused to transmit a data message including an acknowledgment of the received macro definition message and the generated order macro ID.
 5. The system of claim 1, wherein the system is further caused to: parse the one or more first fields and the one or more second fields in the first order data message; and validate all of the one or more first fields in the first order data message.
 6. The system of claim 1, wherein the complete order is generated by concatenating the first field values with the third field values.
 7. The system of claim 1, wherein the first order data message and the second order data message are processed using a same protocol.
 8. The system of claim 1, wherein the order data included in the complete order is processed by (a) matching the order data with order data included in the memory, or (b) storing the order data in the memory for later matching.
 9. The system of claim 1, wherein the second order data message includes fewer fields than the first order data message.
 10. The system of claim 1, wherein the first order includes an initial order, the one or more first fields are static fields, and the one or more second fields are variable fields.
 11. A method for processing order data message, the method comprising: in an information processing system having at least a processor and a memory: receiving a first order data message, wherein the first order data message includes: one or more first fields; one or more second fields; and a first order having first field values associated with the one or more first fields and second field values associated with the one or more second fields; generating a first order template having the one or more first fields and the one or more second fields, the one or more first fields in the first order template including the first field values; receiving a second order data message, wherein the second order data message is associated with the first order and includes third field values associated with the one or more second fields; and generating a complete order based on the validated third field values in the second order data message and the first field values in the first order template.
 12. The method of claim 11, further comprising: validating the third field values in the second order data message; and process order data included in the complete order.
 13. The method of claim 12, wherein the complete order is generated by concatenating the first field values with the third field values.
 14. The method of claim 12, wherein the first order template is a macro definition message, and the macro definition message includes the one or more first fields, the one or more second fields, and the first order having the first and second field values.
 15. The method of claim 14, wherein the second order data message references the macro definition message using an order macro identifier (ID).
 16. The method of claim 15, wherein the system is further caused to transmit a data message including an acknowledgment of the received macro definition message and the generated order macro ID.
 17. A client system, comprising: a processor; and a memory configured to store computer readable instructions that, when executed by the processor, cause the client system to: create a first order data message, wherein the first order data message includes: one or more first fields; one or more second fields; and a first order having first field values associated with the one or more first fields and second field values associated with the one or more second fields; transmit the first order data message to a server system; receive an acknowledgement message from the server system, wherein the acknowledgement message indicates receipt of the first order data message; create a second order data message, wherein the second order data message is associated with the first order and includes third field values associated with the one or more second fields; and transmit the second order data message to the server system.
 18. The client system of claim 17, wherein the acknowledgement message includes a template identifier associated with a first order template.
 19. The client system of claim 18, wherein the second order data message includes the template identifier associated with the first order template.
 20. The client system of claim 17, wherein the first order data message is an initial order data message, the one or more first fields are static fields, and the one or more second fields are variable fields. 